Please refer to RP-213600 for detailed scope of the WI on NR support for UAV.
R1-2210697 Session notes for 9.15 (NR support for Uncrewed Aerial Vehicles) Ad-Hoc Chair (Huawei)
R1-2209085 Work plan for Rel-18 Uncrewed Aerial Vehicles Rapporteur (Nokia)
R1-2209762 Discussion on the benefits of UE beamforming capability reporting Samsung
· Proposal 1: Further clarification is required whether UE capability reporting of UAV beamforming can achieve any gain without modification on beam management/reporting schemes
· Proposal 2: UE capability reporting of UAV beamforming is not supported as Rel-18 work, unless gain of capability reporting is confirmed without additional L1 reporting.
Decision: The document is noted.
R1-2209631 UE capability and RRC signaling for UAV beamforming Nokia, Nokia Shanghai Bell
· Proposal 1: Study the applicability and need to adapt the definitions for OTA coverage range and OTA peak directions set for the AV UE to be checked (FFS).
· Proposal 2: Define several AV UE reference beam directions (see for example Figure 1) i.e., information for several beam direction pairs (beam centre direction and the related beam peak direction) need to be included in the AV UE capability signalling, each with an unique beam identity.
· Proposal 3: Specify the beamwidth for each beam direction pair as an index in a pre-defined set of generic beamwidths values (FFS).
· Proposal 4: Specify for each beam direction pair a beam gain parameter as an index in a pre-defined set of beam gains values (FFS)
· Proposal 5: Study how to provide AV UE antenna radiated characteristics to the serving network, including both manufacturer declared parameter values, initial capability signaling and signalling during connected mode.
Decision: The document is noted.
R1-2208674 Discussion on UE capability and RRC signaling for UAV beamforming vivo
· Decide whether Rel-15/16 beam indication framework or Rel-17 unified TCI framework is used for beamforming in UAV scenario.
· To support beamforming for UAV UE in FR1, consider removing the restriction applicable only to FR2 for some UE capability parameters related to beam management. Send LS to RAN2.
· To support beamforming for UAV UE in FR1, consider allowing to configure QCL Type D for a second QCL type associated with a reference RS in a TCI state. Update RAN1 specification accordingly.
Decision: The document is noted.
R1-2208405 UE capability and RRC signaling for UAV beamforming Huawei, HiSilicon
R1-2208697 Discussion on UE capability for UAV beamforming ZTE
R1-2208749 Discussion on UE capability and RRC signaling for UAV beamforming Lenovo
R1-2209274 Discussion on UE capability and RRC signaling for UAV beamforming xiaomi
R1-2209928 Discussion on UE capability and RRC signaling for UAV beamforming NTT DOCOMO, INC.
R1-2210016 Discussion of UE capability and RRC signaling for UAV beamforming Qualcomm Incorporated
R1-2210092 On UAV beamforming capabilities Ericsson
[110bis-e-R18-UAV-01] Email discussion on UE capability and RRC signaling for UAV beamforming by October 19 Kevin (Nokia)
- Check points: October 14, October 19
R1-2210310 Summary#1 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
R1-2210311 Summary#2 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From Oct 19th GTW session
Agreement
Study extending application of FR2-only beam management parameters e.g., spatial relation, beam correspondence, etc. to FR1 for UAV UEs
· FFS: Other parameters
· FFS: Impacts to legacy beam management for FR1
· FFS: Application of beam correspondence in FDM bands
Note: Identification of relevant UAV UE capabilities does not require commitment to support a specific TCI framework, and relevant parameters may change depending on the framework supported
Note: Whether or not to specify above parameters should depend on the identification of the target scenarios and the potential issues faced by UAV, the identification of which existing capabilities and/or mechanisms and/or frameworks can be treated as candidate for addressing above issues, and the necessity of specifying above parameters (i.e., whether the potential issues faced by UAV can already be solved with the existing capabilities and/or mechanisms and/or frameworks)
Agreement
Study indication of beam characteristics, e.g., number of beams, beamwidth, beam center, radiated EIRP, etc. as UAV UE capability
· FFS: Feasibility/benefit of indicating orientation of beams including height dependence
· FFS: Necessary parameters, ranges of suitable values, and method of indication
· FFS: Height-dependence on relevant parameters
· FFS: Indication of beams as either fixed or adaptive
Note: Whether or not to specify above parameters should depend on the identification of the target scenarios and the potential issues faced by UAV, the identification of which existing capabilities and/or mechanisms and/or frameworks can be treated as candidate for addressing above issues, and the necessity of specifying above parameters (i.e., whether the potential issues faced by UAV can already be solved with the existing capabilities and/or mechanisms and/or frameworks)
Agreement
Study indication of minimum beam application latency as UAV UE capability
· If unifiedJointTCI-r17 is supported, suitable range of values for minBeamApplicationTime-r17
· If unifiedJointTCI-r17 is not supported, enhancements to timedurationforQCL may be considered
· FFS: additional parameters, e.g., beamSwitchTiming
Note: further consideration does not require commitment to support a specific TCI framework.
Note: Whether or not to specify above parameters should depend on the identification of the target scenarios and the potential issues faced by UAV, the identification of which existing capabilities and/or mechanisms and/or frameworks can be treated as candidate for addressing above issues, and the necessity of specifying above parameters (i.e., whether the potential issues faced by UAV can already be solved with the existing capabilities and/or mechanisms and/or frameworks)
Final summary in R1-2210312.
Please refer to RP-213600 for detailed scope of the WI on NR support for UAV. This agenda item will not be treated in RAN1#111. No contributions please.
Please refer to RP-223545 for detailed scope of the WI on NR support for UAV.
R1-2302070 Session notes for 9.15 (NR support for UAV (Uncrewed Aerial Vehicles) Ad-Hoc Chair (Huawei)
[112-R18-UAV] Kevin (Nokia)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2300132 UE capability and RRC signaling for UAV beamforming Huawei, HiSilicon
R1-2300482 Discussion on UE capability and RRC signaling for UAV beamforming vivo
R1-2300519 Discussion on UE capability and RRC signaling for UAV beamforming Lenovo
R1-2300564 Discussion on UE capability and RRC signaling for UAV beamforming xiaomi
R1-2300708 Discussion on UE capability for UAV beamforming ZTE
R1-2300713 Discussion on UE capability and RRC signaling for UAV beamforming Nokia, Nokia Shanghai Bell
R1-2301295 Discussion on UE capability and RRC signaling for UAV beamforming Samsung
R1-2301377 On UE capability and RRC signaling for UAV beamforming Apple
R1-2301444 Discussion of UE capability and RRC signaling for UAV beamforming Qualcomm Incorporated
R1-2301522 Discussion on UE capability and RRC signaling for UAV beamforming NTT DOCOMO, INC.
R1-2301629 On UAV beamforming capabilities Ericsson
R1-2301953 Summary#1 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From Monday session
Agreement
RAN1 only considers potential UE UAV beamforming capabilities for FR1 with directional antennas at UE side in Rel-18 if such capabilities dont impact RAN4 requirements.
Agreement
If new UE UAV beamforming capabilities for FR1 with directional antennas at UE side are supported, Rel-17 unified TCI framework is considered as baseline.
Agreement
Multi-TRP beamforming is not supported for UAV UEs in FR1 in Rel-18.
R1-2301954 Summary#2 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From Wednesday session
Agreement
UE UAV beamforming for FR1 based on beam switching among fixed directional antennas is supported in Rel-18.
· Note 1: new UE capabilities may not be necessary to support beam switching among fixed directional antennas
· Note 2: no RAN4 specification impact is assumed
· FFS: whether updating (e.g. extending to FR1) legacy UE capabilities is needed, and it is not precluded if it is needed
· FFS: whether/how specification may be impacted
Final summary in R1-2301955.
Please refer to RP-230782 for detailed scope of the WI on NR support for UAV.
R1-2304175 Session notes for 9.13 (NR support for UAV (Uncrewed Aerial Vehicles) Ad-Hoc Chair (Huawei)
R1-2302345 UE capability and RRC signaling for UAV beamforming Huawei, HiSilicon
R1-2302512 Discussion on UE capability and RRC signaling for UAV beamforming vivo
R1-2302732 Discussion on UE capability and RRC signaling for UAV beamforming Lenovo
R1-2302866 Discussion on UE capability and RRC signaling for UAV beamforming Sony
R1-2303156 Discussion on UE capability and RRC signaling for UAV beamforming Samsung
R1-2303298 Discussion on UE capability for UAV beamforming ZTE
R1-2303418 Discussion on UE capability and RRC signaling for UAV beamforming Nokia, Nokia Shanghai Bell
R1-2303511 On UE capability and RRC signaling for UAV beamforming Apple
R1-2303618 Discussion of UE capability and RRC signaling for UAV beamforming Qualcomm Incorporated
R1-2303734 Discussion on UE capability and RRC signaling for UAV beamforming NTT DOCOMO, INC.
R1-2303785 On UAV beamforming capabilities Ericsson
[112bis-e-R18-UAV-01] Kevin (Nokia)
Email discussion on UE capability and RRC signaling for UAV beamforming by April 26 - extended till April 28th
- Check points: April 21, April 26
R1-2304038 Summary#1 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From April 18th GTW session
Conclusion
It is RAN1's understanding that beam correspondence for a UE UAV operating in FR1 (if introduced) based on fixed directional antennas would not require the definition of radiated requirements in RAN4, where beam correspondence means that the UE uses the same fixed directional antenna for transmitting and receiving.
R1-2304039 Summary#2 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From April 20th GTW session
Conclusion
One identified use case for UE UAVs in Rel-18 includes beam switching among fixed directional antennas at least to limit interference and balance traffic load to adjacent cells.
R1-2304040 Summary#3 of discussion on UAV capability and RRC signaling for UAV Moderator (Nokia)
From April 24th GTW session
Conclusion
Without new UE capability, using legacy BM/SRI framework, the network cannot be aware that a UAV UE is using fixed directional antennas or an omnidirectional antenna.
Decision: As per email decision posted on April 28th,
Conclusion
There is no consensus on whether new UE UAV capabilities including beam related information, beam correspondence, or QCL Type-D should be reported and whether reporting the UE UAV beamforming capabilities only is sufficient or not to support beamforming based on beam switching among fixed directional antennas to limit interference and/or balance traffic load to adjacent cells in FR1 in Rel-18.